Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a4266ba2c7f1b82bd438eda2e6ad6910c3c1e71b9761143ae7eaa163c571da

Tx prefix hash: bf573cb7bbb35fdda5a1a175a3ae86fde2eb9efeebf4f6f87541320422735f86
Tx public key: 970be5f562db46e4ad307cb4e40f349444f1f4caea2d7b59200e168edec99628
Timestamp: 1704893140 Timestamp [UCT]: 2024-01-10 13:25:40 Age [y:d:h:m:s]: 01:046:08:22:10
Block: 932305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294191 RingCT/type: yes/0
Extra: 01970be5f562db46e4ad307cb4e40f349444f1f4caea2d7b59200e168edec9962802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790798cd57a9ad11e1ca0efe58c4076117d52623fb6f0ba40f4957628928b160 0.600000000000 1390237 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": 932315, "vin": [ { "gen": { "height": 932305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790798cd57a9ad11e1ca0efe58c4076117d52623fb6f0ba40f4957628928b160" } } ], "extra": [ 1, 151, 11, 229, 245, 98, 219, 70, 228, 173, 48, 124, 180, 228, 15, 52, 148, 68, 241, 244, 202, 234, 45, 123, 89, 32, 14, 22, 142, 222, 201, 150, 40, 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