Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed06309bf7a5dda3707ce2eff602fe643ed6ea978f5b96071d92b280a5532cd

Tx prefix hash: 166b3b06d6c186187a9b38d74ce85c41ba7f3ca62ea39f466c85a63ebb684f65
Tx public key: 67003f25b604395f99d7389cb94dd56221a38608d8aa69bba32cd623b89f5d47
Timestamp: 1740842822 Timestamp [UTC]: 2025-03-01 15:27:02 Age [y:d:h:m:s]: 01:263:09:22:01
Block: 1229891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452386 RingCT/type: yes/0
Extra: 0167003f25b604395f99d7389cb94dd56221a38608d8aa69bba32cd623b89f5d470211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b0d0a1679321007131f446f22b8f074ef7e961f9e7ea0d788dd94f962bc1313 0.000600000000 1716782 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": 1229901, "vin": [ { "gen": { "height": 1229891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0d0a1679321007131f446f22b8f074ef7e961f9e7ea0d788dd94f962bc1313" } } ], "extra": [ 1, 103, 0, 63, 37, 182, 4, 57, 95, 153, 215, 56, 156, 185, 77, 213, 98, 33, 163, 134, 8, 216, 170, 105, 187, 163, 44, 214, 35, 184, 159, 93, 71, 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: