Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd990d4331e641a1a076ff46cbebeebb9c9be48d0f2c3a87c283c7f21cbcb70c

Tx prefix hash: 57af548a74d2fc25318b3574cf2cc3c843785de1b079d70f9bd1a66dd059db65
Tx public key: b80fd554fbc3ddda0454196d3763935d5428e8643d662ca01f94a51e5afb6e76
Timestamp: 1771628093 Timestamp [UTC]: 2026-02-20 22:54:53 Age [y:d:h:m:s]: 00:269:18:32:18
Block: 1482231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198295 RingCT/type: yes/0
Extra: 01b80fd554fbc3ddda0454196d3763935d5428e8643d662ca01f94a51e5afb6e76021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 361ba1bda5f320e90db89bc73d2fd08b900960641486bd39c01bbc4db1cc8315 0.000600000000 1971621 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": 1482241, "vin": [ { "gen": { "height": 1482231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "361ba1bda5f320e90db89bc73d2fd08b900960641486bd39c01bbc4db1cc8315" } } ], "extra": [ 1, 184, 15, 213, 84, 251, 195, 221, 218, 4, 84, 25, 109, 55, 99, 147, 93, 84, 40, 232, 100, 61, 102, 44, 160, 31, 148, 165, 30, 90, 251, 110, 118, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: