Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5c2bc3d6bbcbda7ad75c04dd3f5aac6722fab0869a8de7e186bcdc57df2bbe6

Tx prefix hash: 7aac019758be7527054393c96047ab458409d0d180824ccc7f4b71a9148a2a19
Tx public key: ed7940fbb9f18406ff39c93aa649f4e72e6756339abcc0e98a0ea48abf644014
Timestamp: 1749968659 Timestamp [UTC]: 2025-06-15 06:24:19 Age [y:d:h:m:s]: 00:347:03:38:45
Block: 1305350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239890 RingCT/type: yes/0
Extra: 01ed7940fbb9f18406ff39c93aa649f4e72e6756339abcc0e98a0ea48abf644014021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4356c492fabe1810924f615723e7e5a701105bb78c24f4a5cbf2c304c3440764 0.000600000000 1792949 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": 1305360, "vin": [ { "gen": { "height": 1305350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4356c492fabe1810924f615723e7e5a701105bb78c24f4a5cbf2c304c3440764" } } ], "extra": [ 1, 237, 121, 64, 251, 185, 241, 132, 6, 255, 57, 201, 58, 166, 73, 244, 231, 46, 103, 86, 51, 154, 188, 192, 233, 138, 14, 164, 138, 191, 100, 64, 20, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: