Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56122eeb69d0d2a506b1b35120505b90c9e5d63c047d7bfa88976d7e403fee9

Tx prefix hash: f603c67ba68a40e2f684506b8df90869f0dd1517ed563debc8bc1e225ffe2193
Tx public key: 378c1e98aecdca4c1e1167e0ebef850dfd4a997843d94eb85abaf04df4e99d53
Timestamp: 1771874938 Timestamp [UTC]: 2026-02-23 19:28:58 Age [y:d:h:m:s]: 00:268:23:48:14
Block: 1484273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197828 RingCT/type: yes/0
Extra: 01378c1e98aecdca4c1e1167e0ebef850dfd4a997843d94eb85abaf04df4e99d53021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 969718eb795f07b9995b7a011acab9656a58a0e753838a2df74480cef11bef4e 0.000600000000 1973693 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": 1484283, "vin": [ { "gen": { "height": 1484273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "969718eb795f07b9995b7a011acab9656a58a0e753838a2df74480cef11bef4e" } } ], "extra": [ 1, 55, 140, 30, 152, 174, 205, 202, 76, 30, 17, 103, 224, 235, 239, 133, 13, 253, 74, 153, 120, 67, 217, 78, 184, 90, 186, 240, 77, 244, 233, 157, 83, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: