Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f326f855acc1eb8e92a6f9ef3ee9aa2cd6fcd312217d6bf7e2026abc7e50503

Tx prefix hash: 34387b0b566556d8b79e42515492bd1d8009da30589274cd87ee06759ee6296f
Tx public key: 8372465a922ca20c7253985aa59011b67b61c221d4335b0f29e3e5d14d78d148
Timestamp: 1771475794 Timestamp [UTC]: 2026-02-19 04:36:34 Age [y:d:h:m:s]: 00:271:13:49:49
Block: 1480965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199593 RingCT/type: yes/0
Extra: 018372465a922ca20c7253985aa59011b67b61c221d4335b0f29e3e5d14d78d148021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 201cee528db0ac48ad77ae3b1ad436f000b63f2d636c84f69a8423cf3620d164 0.000600000000 1970337 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": 1480975, "vin": [ { "gen": { "height": 1480965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "201cee528db0ac48ad77ae3b1ad436f000b63f2d636c84f69a8423cf3620d164" } } ], "extra": [ 1, 131, 114, 70, 90, 146, 44, 162, 12, 114, 83, 152, 90, 165, 144, 17, 182, 123, 97, 194, 33, 212, 51, 91, 15, 41, 227, 229, 209, 77, 120, 209, 72, 2, 17, 0, 0, 0, 2, 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: