Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540032b5781d79a319e74143222eb80618e3cb6990040b3c45b5d2826aac571d

Tx prefix hash: 57d81315bfa077ea1950ec5cb2432c96c97ce19c0de9e0fdec8247403a29d2ce
Tx public key: 2db89ce566aff99e3bb3283512f726c55c1b4548e4d37f906a9a06e3d19c89f5
Timestamp: 1705381833 Timestamp [UCT]: 2024-01-16 05:10:33 Age [y:d:h:m:s]: 00:360:23:38:56
Block: 936340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258454 RingCT/type: yes/0
Extra: 012db89ce566aff99e3bb3283512f726c55c1b4548e4d37f906a9a06e3d19c89f50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcce4a938339b1f3f0c3971b7669cc6d8c0dfb3728c7f458e51468c9f471f368 0.600000000000 1394364 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": 936350, "vin": [ { "gen": { "height": 936340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcce4a938339b1f3f0c3971b7669cc6d8c0dfb3728c7f458e51468c9f471f368" } } ], "extra": [ 1, 45, 184, 156, 229, 102, 175, 249, 158, 59, 179, 40, 53, 18, 247, 38, 197, 92, 27, 69, 72, 228, 211, 127, 144, 106, 154, 6, 227, 209, 156, 137, 245, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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