Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d865d7b3d959a4edbc59ea6ca587b9cef1540e528f91826be0a704a1f91e884c

Tx prefix hash: c3c1ac0426784ce7735a02a5aba7dd6bd988a09b6c80b4e45fa271590635a8e7
Tx public key: 2fff54523fee2550b38bacf940f8d0fec021fc5c63f7ae99634dbf4ac3db9587
Timestamp: 1718405608 Timestamp [UCT]: 2024-06-14 22:53:28 Age [y:d:h:m:s]: 00:274:00:24:52
Block: 1044339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195834 RingCT/type: yes/0
Extra: 012fff54523fee2550b38bacf940f8d0fec021fc5c63f7ae99634dbf4ac3db958702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92f0454be2ae6b2b4ed80ed96fe65da332aad2a7d0399c97321cde36deb83d43 0.600000000000 1513620 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": 1044349, "vin": [ { "gen": { "height": 1044339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92f0454be2ae6b2b4ed80ed96fe65da332aad2a7d0399c97321cde36deb83d43" } } ], "extra": [ 1, 47, 255, 84, 82, 63, 238, 37, 80, 179, 139, 172, 249, 64, 248, 208, 254, 192, 33, 252, 92, 99, 247, 174, 153, 99, 77, 191, 74, 195, 219, 149, 135, 2, 17, 0, 0, 0, 3, 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