Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1d1024cff6c30d6685f45f88a4e2b62af3f3c0ac140c175f1a132618df2b92

Tx prefix hash: e40af1f6034bfe445b9dea010ceac03b3c903ce514db2f3c3e63cba11e038bae
Tx public key: 4ae0552301984d061607f99daed3722fded3da297a5f9972221cef032aaa58c1
Timestamp: 1743208029 Timestamp [UTC]: 2025-03-29 00:27:09 Age [y:d:h:m:s]: 00:324:15:21:07
Block: 1249478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229660 RingCT/type: yes/0
Extra: 014ae0552301984d061607f99daed3722fded3da297a5f9972221cef032aaa58c10211000000011a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5e1a888771d1a43ead15b060a6c272032dc448afcbba0fb0c415e24421897a53 0.000600000000 1736517 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": 1249488, "vin": [ { "gen": { "height": 1249478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e1a888771d1a43ead15b060a6c272032dc448afcbba0fb0c415e24421897a53" } } ], "extra": [ 1, 74, 224, 85, 35, 1, 152, 77, 6, 22, 7, 249, 157, 174, 211, 114, 47, 222, 211, 218, 41, 122, 95, 153, 114, 34, 28, 239, 3, 42, 170, 88, 193, 2, 17, 0, 0, 0, 1, 26, 151, 4, 3, 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) | dinastycoin version: tesla-369