Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80acf49672edac127b25fd088b913180d5c7fb559c16714028b9e8791dfb9768

Tx prefix hash: 244dfe21f79414501c0bdf89a06902c333c18baaf0d784ec15a7f2730ecd4243
Tx public key: 1d886c923a73eef906f8d71a2a1a0a52bf6a4ceffe75d22fa7792e1410ab1ea3
Timestamp: 1715590493 Timestamp [UCT]: 2024-05-13 08:54:53 Age [y:d:h:m:s]: 00:287:22:05:29
Block: 1021018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205745 RingCT/type: yes/0
Extra: 011d886c923a73eef906f8d71a2a1a0a52bf6a4ceffe75d22fa7792e1410ab1ea302110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b765dc2daf0181a84ec1d7012349cd513e12b33f1023774152ce555f60dd251 0.600000000000 1485181 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": 1021028, "vin": [ { "gen": { "height": 1021018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b765dc2daf0181a84ec1d7012349cd513e12b33f1023774152ce555f60dd251" } } ], "extra": [ 1, 29, 136, 108, 146, 58, 115, 238, 249, 6, 248, 215, 26, 42, 26, 10, 82, 191, 106, 76, 239, 254, 117, 210, 47, 167, 121, 46, 20, 16, 171, 30, 163, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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