Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bb06f9dbe3f33d1fc0fc2d636afa62547d532fd07154857eeddc9a3b64fb1b

Tx prefix hash: 22ca7203ecdad3f8df9105fa1744a5cf584b844d55906bc54e0f9e9efd495695
Tx public key: 826757d46ef9926a72d10798bbc047a329ce5bfaa71caaee6aa71ac83f957272
Timestamp: 1771545324 Timestamp [UTC]: 2026-02-19 23:55:24 Age [y:d:h:m:s]: 00:270:16:08:18
Block: 1481545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198934 RingCT/type: yes/0
Extra: 01826757d46ef9926a72d10798bbc047a329ce5bfaa71caaee6aa71ac83f957272021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ef911b9fd3549e4ea7bd08603460eca7561c3d33b49ff70e53c733e81134a96 0.000600000000 1970927 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": 1481555, "vin": [ { "gen": { "height": 1481545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef911b9fd3549e4ea7bd08603460eca7561c3d33b49ff70e53c733e81134a96" } } ], "extra": [ 1, 130, 103, 87, 212, 110, 249, 146, 106, 114, 209, 7, 152, 187, 192, 71, 163, 41, 206, 91, 250, 167, 28, 170, 238, 106, 167, 26, 200, 63, 149, 114, 114, 2, 17, 0, 0, 0, 6, 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: