Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ff34738ff5ae891e1157eb327a52f5aac59de7b93babf6546d597535679610

Tx prefix hash: 9f079f91919dcfaa2c0d967b49adab0fc74fe41979151ef54ac17a44593a8720
Tx public key: 32f0d15ea63a4c40c09aee0c649a567e31d9b2e7143b217cddb5efd783bdee25
Timestamp: 1714686810 Timestamp [UCT]: 2024-05-02 21:53:30 Age [y:d:h:m:s]: 00:252:15:45:57
Block: 1013509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180835 RingCT/type: yes/0
Extra: 0132f0d15ea63a4c40c09aee0c649a567e31d9b2e7143b217cddb5efd783bdee2502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df9684e17e4886e4a74315f7d9d55ce3f2d605fb56e302467ddd9e540823867f 0.600000000000 1476344 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": 1013519, "vin": [ { "gen": { "height": 1013509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df9684e17e4886e4a74315f7d9d55ce3f2d605fb56e302467ddd9e540823867f" } } ], "extra": [ 1, 50, 240, 209, 94, 166, 58, 76, 64, 192, 154, 238, 12, 100, 154, 86, 126, 49, 217, 178, 231, 20, 59, 33, 124, 221, 181, 239, 215, 131, 189, 238, 37, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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