Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87860cf30f5d072678128d5cff892df8723301b2790c6c392908794407d4814

Tx prefix hash: d0b2a1c5354cba0e2ca29275df0f03e9957bf90f4209c9ead79268b3c378af4e
Tx public key: 9a65eecb1bf62d7ee2394c88f478a775c27fd54ad8dc82dcfc5994bf867de5e8
Timestamp: 1718183754 Timestamp [UCT]: 2024-06-12 09:15:54 Age [y:d:h:m:s]: 00:309:02:51:12
Block: 1042506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220905 RingCT/type: yes/0
Extra: 019a65eecb1bf62d7ee2394c88f478a775c27fd54ad8dc82dcfc5994bf867de5e80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ddf0652479855ea01eaa12064b2114fb55255e4959b4b774277e0f9d119da89 0.600000000000 1511443 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": 1042516, "vin": [ { "gen": { "height": 1042506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ddf0652479855ea01eaa12064b2114fb55255e4959b4b774277e0f9d119da89" } } ], "extra": [ 1, 154, 101, 238, 203, 27, 246, 45, 126, 226, 57, 76, 136, 244, 120, 167, 117, 194, 127, 213, 74, 216, 220, 130, 220, 252, 89, 148, 191, 134, 125, 229, 232, 2, 17, 0, 0, 0, 4, 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