Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b022e6e4e022fc2e00d5a14195766c862f6c09cfc94be18bfc8f538ff9dc87b9

Tx prefix hash: 559d74b7feeb8e17f4760ecd0b0603063ae7fcbbce0cfa5e2a947b1dbbc8eb8c
Tx public key: 3ed99c7cba80a926a333576eabd9722c11287b19f74ea136c8d32a342ff156d7
Timestamp: 1742260846 Timestamp [UTC]: 2025-03-18 01:20:46 Age [y:d:h:m:s]: 01:248:11:20:42
Block: 1241650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441757 RingCT/type: yes/0
Extra: 013ed99c7cba80a926a333576eabd9722c11287b19f74ea136c8d32a342ff156d70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 135e49e0c4c8f0734d4714c8460aeacbd5d9f53e105240f8e7648f96f80cc6a4 0.000600000000 1728623 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": 1241660, "vin": [ { "gen": { "height": 1241650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135e49e0c4c8f0734d4714c8460aeacbd5d9f53e105240f8e7648f96f80cc6a4" } } ], "extra": [ 1, 62, 217, 156, 124, 186, 128, 169, 38, 163, 51, 87, 110, 171, 217, 114, 44, 17, 40, 123, 25, 247, 78, 161, 54, 200, 211, 42, 52, 47, 241, 86, 215, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: