Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdef560bc6246bdc65b9e0fe14bc2f96e3daf8ecf1972854a270ef5635f184cf

Tx prefix hash: 61fed4383969f6d4774c84a285e39da391a4d10cc61623a6b29d0f6e109aa87e
Tx public key: 15afe211c1e0ca23053af84b0c354c71fd44c0d37448c221b85b6f30c4d86cfc
Timestamp: 1724622432 Timestamp [UCT]: 2024-08-25 21:47:12 Age [y:d:h:m:s]: 00:295:14:53:53
Block: 1095876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211084 RingCT/type: yes/0
Extra: 0115afe211c1e0ca23053af84b0c354c71fd44c0d37448c221b85b6f30c4d86cfc021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a574626760fc8a1f6bf4754e7990c7ef8198b0f7654451d6604d9b29301ed107 0.600000000000 1571059 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": 1095886, "vin": [ { "gen": { "height": 1095876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a574626760fc8a1f6bf4754e7990c7ef8198b0f7654451d6604d9b29301ed107" } } ], "extra": [ 1, 21, 175, 226, 17, 193, 224, 202, 35, 5, 58, 248, 75, 12, 53, 76, 113, 253, 68, 192, 211, 116, 72, 194, 33, 184, 91, 111, 48, 196, 216, 108, 252, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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