Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d0c5439e43957d1ce328f971fbcc9332a24ffd465ef3e0c576e48cd83cdc2a

Tx prefix hash: 03b48bf2336614b0b15393e0b66d87ec22b77d28775bfce109c2b0f76b2ac95d
Tx public key: 0f050abd6a080608b4380d4af40c48002a5d52c74e6ad7e1336fe1df103045f9
Timestamp: 1774711812 Timestamp [UTC]: 2026-03-28 15:30:12 Age [y:d:h:m:s]: 00:234:18:35:08
Block: 1507739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173315 RingCT/type: yes/0
Extra: 010f050abd6a080608b4380d4af40c48002a5d52c74e6ad7e1336fe1df103045f9021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 24d0054765e7a6a94afa052744067eacf091ab3c4eafb417130e364f6f8c5b1c 0.000600000000 1997491 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": 1507749, "vin": [ { "gen": { "height": 1507739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24d0054765e7a6a94afa052744067eacf091ab3c4eafb417130e364f6f8c5b1c" } } ], "extra": [ 1, 15, 5, 10, 189, 106, 8, 6, 8, 180, 56, 13, 74, 244, 12, 72, 0, 42, 93, 82, 199, 78, 106, 215, 225, 51, 111, 225, 223, 16, 48, 69, 249, 2, 17, 0, 0, 0, 5, 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: