Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd80c54e026ad7ef661d132ec626a75f3b56f13a9aa777d71fc395d4d2f345bf

Tx prefix hash: eada213e1253d12764c797a51cf3458401245b080a4fc8b621d2013e2751c4ac
Tx public key: a3e4a4dad269638d426256204886c5a98727d328b77f0d52525b863ccd03bc2a
Timestamp: 1746134704 Timestamp [UTC]: 2025-05-01 21:25:04 Age [y:d:h:m:s]: 01:202:16:20:15
Block: 1273702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409031 RingCT/type: yes/0
Extra: 01a3e4a4dad269638d426256204886c5a98727d328b77f0d52525b863ccd03bc2a021100000003a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78e1eca0959d50b7a00c88f8667a246c8028abf4663209d27e989ea0a537fd78 0.000600000000 1760985 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": 1273712, "vin": [ { "gen": { "height": 1273702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78e1eca0959d50b7a00c88f8667a246c8028abf4663209d27e989ea0a537fd78" } } ], "extra": [ 1, 163, 228, 164, 218, 210, 105, 99, 141, 66, 98, 86, 32, 72, 134, 197, 169, 135, 39, 211, 40, 183, 127, 13, 82, 82, 91, 134, 60, 205, 3, 188, 42, 2, 17, 0, 0, 0, 3, 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: