Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ca0f2a75e5aa445dd6c7a642b774ce663aa442cf4eb7367fbf65369e8d541f

Tx prefix hash: 81040e4ec1767995aa34e8dcfc81c832582fc6fe4cf635f8102500d0f5e7efaf
Tx public key: 1d9031eb0076851fdf258f927bf593e468dbf3f19b700834b2e658626f946dc0
Timestamp: 1713373279 Timestamp [UCT]: 2024-04-17 17:01:19 Age [y:d:h:m:s]: 01:197:03:26:51
Block: 1002614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399556 RingCT/type: yes/0
Extra: 011d9031eb0076851fdf258f927bf593e468dbf3f19b700834b2e658626f946dc002110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b9af35fd42ce5f7e68331e26945aa79c5d0cce024362ff5fab1395579c67e7 0.600000000000 1463132 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": 1002624, "vin": [ { "gen": { "height": 1002614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b9af35fd42ce5f7e68331e26945aa79c5d0cce024362ff5fab1395579c67e7" } } ], "extra": [ 1, 29, 144, 49, 235, 0, 118, 133, 31, 223, 37, 143, 146, 123, 245, 147, 228, 104, 219, 243, 241, 155, 112, 8, 52, 178, 230, 88, 98, 111, 148, 109, 192, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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