Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a9cd410078ed5e1be1ca826284700993d29fe22b544835b7f66a6a50f2a36a

Tx prefix hash: 7d72d22204a8758c5e71399593692c630f05a6c4a56f47b57484412d00897828
Tx public key: 481a1d719ccd02c10ad0e1df0908e41e56e86e5385e816fff4c72f950c689148
Timestamp: 1741083195 Timestamp [UTC]: 2025-03-04 10:13:15 Age [y:d:h:m:s]: 01:260:17:04:07
Block: 1231883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450474 RingCT/type: yes/0
Extra: 01481a1d719ccd02c10ad0e1df0908e41e56e86e5385e816fff4c72f950c68914802110000000a007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c5028d6013d660108734eea47ed47ce50652a673b2f41b012bc88a46fd34f11b 0.000600000000 1718794 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": 1231893, "vin": [ { "gen": { "height": 1231883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5028d6013d660108734eea47ed47ce50652a673b2f41b012bc88a46fd34f11b" } } ], "extra": [ 1, 72, 26, 29, 113, 156, 205, 2, 193, 10, 208, 225, 223, 9, 8, 228, 30, 86, 232, 110, 83, 133, 232, 22, 255, 244, 199, 47, 149, 12, 104, 145, 72, 2, 17, 0, 0, 0, 10, 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: