Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb12c6d84f71fb1ede7abdef6ac1633a9596a6c96597d793c1004447a9d0d5c8

Tx prefix hash: f97ff5631fbedfff12cd157f109277ebf72b54b9aee76eb815c9d393dfea24c3
Tx public key: e8e03efcea59ba0bc662b57db680aa254dbd27510c17aedb9d7b17d07a63a780
Timestamp: 1704628183 Timestamp [UCT]: 2024-01-07 11:49:43 Age [y:d:h:m:s]: 01:303:18:05:56
Block: 930099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475913 RingCT/type: yes/0
Extra: 01e8e03efcea59ba0bc662b57db680aa254dbd27510c17aedb9d7b17d07a63a7800211000000190011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a10df381aa6c5f797ffb08b10a1619ef51fa48fa949c5347cd89ef5d3ad6155 0.600000000000 1387977 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": 930109, "vin": [ { "gen": { "height": 930099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a10df381aa6c5f797ffb08b10a1619ef51fa48fa949c5347cd89ef5d3ad6155" } } ], "extra": [ 1, 232, 224, 62, 252, 234, 89, 186, 11, 198, 98, 181, 125, 182, 128, 170, 37, 77, 189, 39, 81, 12, 23, 174, 219, 157, 123, 23, 208, 122, 99, 167, 128, 2, 17, 0, 0, 0, 25, 0, 17, 5, 91, 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