Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8320172c216df41870349b6c079945ad40bb4d2a5778b9549beb74ca5a76910a

Tx prefix hash: af28b5dbef1baf99df012a1929e481fa86a6f818144d1a8121f993a44baa2494
Tx public key: b1511e01f85b59edb41a0275305a5b7a2e6ea29cefafb0c3b7d13c73e21dfea8
Timestamp: 1711568617 Timestamp [UCT]: 2024-03-27 19:43:37 Age [y:d:h:m:s]: 00:293:07:33:08
Block: 987672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209935 RingCT/type: yes/0
Extra: 01b1511e01f85b59edb41a0275305a5b7a2e6ea29cefafb0c3b7d13c73e21dfea80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcc68bb9b06bafaec12c2720dd3e929f3314e7eea0cb6077b3396a7ee6bf54e6 0.600000000000 1447927 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": 987682, "vin": [ { "gen": { "height": 987672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcc68bb9b06bafaec12c2720dd3e929f3314e7eea0cb6077b3396a7ee6bf54e6" } } ], "extra": [ 1, 177, 81, 30, 1, 248, 91, 89, 237, 180, 26, 2, 117, 48, 90, 91, 122, 46, 110, 162, 156, 239, 175, 176, 195, 183, 209, 60, 115, 226, 29, 254, 168, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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