Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785e3af80aad66d11b530cafe05d85f079ab5da3aba8280ff187040341f2a06c

Tx prefix hash: 8093402de6c7984c571d0f3ba1991e989e189ea995cb20f3ed0e788cf1a59e7a
Tx public key: 8c15f94d911b9832c4ef702659602a9568502810362bc30e174cb511ea8e8db6
Timestamp: 1735321010 Timestamp [UCT]: 2024-12-27 17:36:50 Age [y:d:h:m:s]: 00:077:07:11:28
Block: 1184444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55045 RingCT/type: yes/0
Extra: 018c15f94d911b9832c4ef702659602a9568502810362bc30e174cb511ea8e8db60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76b63f50b0e55ae67824a21fb509c5c5d7a442b56d6fe41f282d7072c2a1e71b 0.600000000000 1670901 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": 1184454, "vin": [ { "gen": { "height": 1184444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76b63f50b0e55ae67824a21fb509c5c5d7a442b56d6fe41f282d7072c2a1e71b" } } ], "extra": [ 1, 140, 21, 249, 77, 145, 27, 152, 50, 196, 239, 112, 38, 89, 96, 42, 149, 104, 80, 40, 16, 54, 43, 195, 14, 23, 76, 181, 17, 234, 142, 141, 182, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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