Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb1dcdee7a37ce424f90727723428d741bef93b6574959e229096ef310031c4

Tx prefix hash: bb3297f028e7edb0110e7519ba577cc1d13ceb140cf0d97344410472b808064f
Tx public key: d58b37ebfa6e25773a99cbc9dc90a1b0df1e8e6340b83752ac4aa325c96724c3
Timestamp: 1726857994 Timestamp [UCT]: 2024-09-20 18:46:34 Age [y:d:h:m:s]: 00:246:05:48:42
Block: 1114406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175857 RingCT/type: yes/0
Extra: 01d58b37ebfa6e25773a99cbc9dc90a1b0df1e8e6340b83752ac4aa325c96724c30211000000035a5c538d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c972b42ce9ed139e76922b44a57abb744aa3ac2976783837a463f8926e7bd847 0.600000000000 1594207 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": 1114416, "vin": [ { "gen": { "height": 1114406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c972b42ce9ed139e76922b44a57abb744aa3ac2976783837a463f8926e7bd847" } } ], "extra": [ 1, 213, 139, 55, 235, 250, 110, 37, 119, 58, 153, 203, 201, 220, 144, 161, 176, 223, 30, 142, 99, 64, 184, 55, 82, 172, 74, 163, 37, 201, 103, 36, 195, 2, 17, 0, 0, 0, 3, 90, 92, 83, 141, 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