Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a126811956ce8f2d848e96a1ca71ba3f5b01fe7564ec85c746f00a654e9974b

Tx prefix hash: 2622f6eb4cd5a2f66db372d69d6ec90449d7f52b03186b693b0dd0d81bad210a
Tx public key: 91f82d92ecbe7d5fee7031d12c8f1849b20bfbc89e3cbf4cdcc8f1f270e9f05e
Timestamp: 1772919553 Timestamp [UTC]: 2026-03-07 21:39:13 Age [y:d:h:m:s]: 00:252:05:38:47
Block: 1492921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185676 RingCT/type: yes/0
Extra: 0191f82d92ecbe7d5fee7031d12c8f1849b20bfbc89e3cbf4cdcc8f1f270e9f05e021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e4ed99402c9153503a7bf5d3bd6ec8eab280fee9659afc69e083aace3deed32 0.000600000000 1982473 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": 1492931, "vin": [ { "gen": { "height": 1492921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4ed99402c9153503a7bf5d3bd6ec8eab280fee9659afc69e083aace3deed32" } } ], "extra": [ 1, 145, 248, 45, 146, 236, 190, 125, 95, 238, 112, 49, 209, 44, 143, 24, 73, 178, 11, 251, 200, 158, 60, 191, 76, 220, 200, 241, 242, 112, 233, 240, 94, 2, 17, 0, 0, 0, 1, 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: