Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e93703acf611bbb8aa04e0197f339d99661aed8185854a3ebe2d9554633b554d

Tx prefix hash: fda5e1084a13cf0bf7e6b45a87a1263d440487e62527c3c16e9080237250a3f4
Tx public key: c92311a8f6c994a9e259b2df865044f98614a28c81514fdf040e899885cc9724
Timestamp: 1725561672 Timestamp [UCT]: 2024-09-05 18:41:12 Age [y:d:h:m:s]: 01:089:11:13:27
Block: 1103670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322397 RingCT/type: yes/0
Extra: 01c92311a8f6c994a9e259b2df865044f98614a28c81514fdf040e899885cc972402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 513c8df44d1dd3dde365d40ea5afd692576e391007d9eb602fd43fc671013e30 0.600000000000 1580587 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": 1103680, "vin": [ { "gen": { "height": 1103670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "513c8df44d1dd3dde365d40ea5afd692576e391007d9eb602fd43fc671013e30" } } ], "extra": [ 1, 201, 35, 17, 168, 246, 201, 148, 169, 226, 89, 178, 223, 134, 80, 68, 249, 134, 20, 162, 140, 129, 81, 79, 223, 4, 14, 137, 152, 133, 204, 151, 36, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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