Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a39727b4a3832b4c026183527d53ab207c0e2f308774849380adad30efdd2c4e

Tx prefix hash: 798aae19f6f9a6744fce3137c8ad8cd2c3f34c5d039d8685b31e654bbd244fb2
Tx public key: 4a1d9c6128b7a9ece823985d516d1bf697af5326614101ec0d4b2632f6d8791f
Timestamp: 1774906922 Timestamp [UTC]: 2026-03-30 21:42:02 Age [y:d:h:m:s]: 00:041:23:12:58
Block: 1509354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22184 RingCT/type: yes/0
Extra: 014a1d9c6128b7a9ece823985d516d1bf697af5326614101ec0d4b2632f6d8791f021100000004ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 27e293d978ed7187acd95de094d37f28e4b2e778b8b20dc09913e44b6e1d2776 0.000600000000 1999126 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": 1509364, "vin": [ { "gen": { "height": 1509354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27e293d978ed7187acd95de094d37f28e4b2e778b8b20dc09913e44b6e1d2776" } } ], "extra": [ 1, 74, 29, 156, 97, 40, 183, 169, 236, 232, 35, 152, 93, 81, 109, 27, 246, 151, 175, 83, 38, 97, 65, 1, 236, 13, 75, 38, 50, 246, 216, 121, 31, 2, 17, 0, 0, 0, 4, 238, 75, 113, 129, 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: