Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c0d50746207f90ec85b92d87d94c6b7cf6538adbf13ffdf073dda84c6ca57a

Tx prefix hash: ae94fbebfa94ae92f75590cd9f37a70b457505a421b2fe00c822af3229e2969a
Tx public key: 654b3f2afb386c020202ee3c697036605a3bf9d22f7e84854bfb3e972a4becfb
Timestamp: 1773868180 Timestamp [UTC]: 2026-03-18 21:09:40 Age [y:d:h:m:s]: 00:243:15:17:58
Block: 1500746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179626 RingCT/type: yes/0
Extra: 01654b3f2afb386c020202ee3c697036605a3bf9d22f7e84854bfb3e972a4becfb021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 047a0be0248b069ce3773cee1a928c5071eac6fb2509c748808873fb5c044b9b 0.000600000000 1990422 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": 1500756, "vin": [ { "gen": { "height": 1500746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "047a0be0248b069ce3773cee1a928c5071eac6fb2509c748808873fb5c044b9b" } } ], "extra": [ 1, 101, 75, 63, 42, 251, 56, 108, 2, 2, 2, 238, 60, 105, 112, 54, 96, 90, 59, 249, 210, 47, 126, 132, 133, 75, 251, 62, 151, 42, 75, 236, 251, 2, 17, 0, 0, 0, 4, 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: