Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c64e956942a0a47ea88a34acebb40737ff36bc32d216383362b7802fad0b584

Tx prefix hash: ca8eb642eaf9d138f11cff2edba2045d8879e586cd782eef32e822a0581b0e3d
Tx public key: 8a0a368bb899c442749c3f0253d81c32759fb6391d42655cb38e4e192dc999c3
Timestamp: 1714890492 Timestamp [UCT]: 2024-05-05 06:28:12 Age [y:d:h:m:s]: 00:348:09:04:40
Block: 1015214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249023 RingCT/type: yes/0
Extra: 018a0a368bb899c442749c3f0253d81c32759fb6391d42655cb38e4e192dc999c30211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499d420c08107c593bff4d0f6a8f920e7c95d437bc1116b5c782e7cff4726ff4 0.600000000000 1478513 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": 1015224, "vin": [ { "gen": { "height": 1015214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499d420c08107c593bff4d0f6a8f920e7c95d437bc1116b5c782e7cff4726ff4" } } ], "extra": [ 1, 138, 10, 54, 139, 184, 153, 196, 66, 116, 156, 63, 2, 83, 216, 28, 50, 117, 159, 182, 57, 29, 66, 101, 92, 179, 142, 78, 25, 45, 201, 153, 195, 2, 17, 0, 0, 0, 7, 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