Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd230ed9cd68232964ceca3ce4169d82bd875247d8bc5584c7912a6550418821

Tx prefix hash: 34bfb32bf58a51e15194f4ec8585d39595ba6ea94635e6a1196b0a60471a2fe2
Tx public key: 30f84c78f5bddd103e6a53c4f1fb7a4e21464f825025251d273e78f5397f9deb
Timestamp: 1711898416 Timestamp [UTC]: 2024-03-31 15:20:16 Age [y:d:h:m:s]: 02:233:23:29:12
Block: 990408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692355 RingCT/type: yes/0
Extra: 0130f84c78f5bddd103e6a53c4f1fb7a4e21464f825025251d273e78f5397f9deb0211000000080011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3c888415fbb3b4470203886d1939d3a4c13b3c0eab2c454b341b114635a7084 0.000600000000 1450730 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": 990418, "vin": [ { "gen": { "height": 990408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c888415fbb3b4470203886d1939d3a4c13b3c0eab2c454b341b114635a7084" } } ], "extra": [ 1, 48, 248, 76, 120, 245, 189, 221, 16, 62, 106, 83, 196, 241, 251, 122, 78, 33, 70, 79, 130, 80, 37, 37, 29, 39, 62, 120, 245, 57, 127, 157, 235, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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: