Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 362ff32ec236280e6a32a1badf9923dcdb5cd8778f6f46deeb508d1bf34577af

Tx prefix hash: efc03f5489562b599dfd0abdc9e04eb099e322066ae13f52aa575c320c403f0c
Tx public key: cdf85e46cee7444b2ba499d6436205730ed6d5d611c07cacfbb3b4d7df5eda4f
Timestamp: 1713624178 Timestamp [UCT]: 2024-04-20 14:42:58 Age [y:d:h:m:s]: 00:204:14:59:24
Block: 1004684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146488 RingCT/type: yes/0
Extra: 01cdf85e46cee7444b2ba499d6436205730ed6d5d611c07cacfbb3b4d7df5eda4f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a43adf4fc8da332b426754c04dc1cd4fdd2230caf31fb5528058fe74b26250d8 0.600000000000 1465254 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1004694, "vin": [ { "gen": { "height": 1004684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a43adf4fc8da332b426754c04dc1cd4fdd2230caf31fb5528058fe74b26250d8" } } ], "extra": [ 1, 205, 248, 94, 70, 206, 231, 68, 75, 43, 164, 153, 214, 67, 98, 5, 115, 14, 214, 213, 214, 17, 192, 124, 172, 251, 179, 180, 215, 223, 94, 218, 79, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8