Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c9d5c9ce4c12090ea5c3b850640ec3e3836f51f40e670b280903583fbb0f0df

Tx prefix hash: 3658706ec5ca78edcbf93048bacbc0b0513aec7e0b2d35be67b281fc69ef34c0
Tx public key: b561160631984aabbafffa0f0108bfe8d1de025313fe88b71a9079c5c4ecce8a
Timestamp: 1731604801 Timestamp [UTC]: 2024-11-14 17:20:01 Age [y:d:h:m:s]: 01:294:03:32:03
Block: 1153676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474581 RingCT/type: yes/0
Extra: 01b561160631984aabbafffa0f0108bfe8d1de025313fe88b71a9079c5c4ecce8a021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 004e529d62d424406083ec066d4da9e489b7a793490a05147504d6e2c57e7d48 0.000600000000 1639287 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 dinastycoin-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": 1153686, "vin": [ { "gen": { "height": 1153676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "004e529d62d424406083ec066d4da9e489b7a793490a05147504d6e2c57e7d48" } } ], "extra": [ 1, 181, 97, 22, 6, 49, 152, 74, 171, 186, 255, 250, 15, 1, 8, 191, 232, 209, 222, 2, 83, 19, 254, 136, 183, 26, 144, 121, 197, 196, 236, 206, 138, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: