Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2511e92b2cdd155de742d30dbf97c845272e5c51c3ae7c1735fee785759ae08

Tx prefix hash: 2adf5ef75646bb4fcc5c36933c0267d699e6557d1d8bbb24768d4c5d400571bf
Tx public key: a68860d8e9c7ec09010e7a335f315da0cbd3642c14eeaf5034e53b59d4704dd6
Timestamp: 1738008034 Timestamp [UCT]: 2025-01-27 20:00:34 Age [y:d:h:m:s]: 00:330:07:49:14
Block: 1206447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233868 RingCT/type: yes/0
Extra: 01a68860d8e9c7ec09010e7a335f315da0cbd3642c14eeaf5034e53b59d4704dd602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0b99da396415daa34e05cc3ad4e266ba24e8da1e5d20dd59f44ecf26c2e1cc9 0.600000000000 1693152 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": 1206457, "vin": [ { "gen": { "height": 1206447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0b99da396415daa34e05cc3ad4e266ba24e8da1e5d20dd59f44ecf26c2e1cc9" } } ], "extra": [ 1, 166, 136, 96, 216, 233, 199, 236, 9, 1, 14, 122, 51, 95, 49, 93, 160, 203, 211, 100, 44, 20, 238, 175, 80, 52, 229, 59, 89, 212, 112, 77, 214, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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