Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0e51996fc6ca6fb9d4a7bc3c40c183431d78ea4203eb46e2e528d41318f236

Tx prefix hash: 4aebb74145c99cf63867cb1864a2d72f7b04635e56a70ad2e3fb672446be5ec6
Tx public key: bb60374f829c01be7ee02aad67a311f79c33de6c62d92dba05d8efb54a9dc9a3
Timestamp: 1771283318 Timestamp [UTC]: 2026-02-16 23:08:38 Age [y:d:h:m:s]: 00:273:10:23:57
Block: 1479362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200938 RingCT/type: yes/0
Extra: 01bb60374f829c01be7ee02aad67a311f79c33de6c62d92dba05d8efb54a9dc9a3021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63496fbf1d24c28c3c17a934e0c15120e4e8663093e9333f3a6c24628062b1bb 0.000600000000 1968710 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": 1479372, "vin": [ { "gen": { "height": 1479362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63496fbf1d24c28c3c17a934e0c15120e4e8663093e9333f3a6c24628062b1bb" } } ], "extra": [ 1, 187, 96, 55, 79, 130, 156, 1, 190, 126, 224, 42, 173, 103, 163, 17, 247, 156, 51, 222, 108, 98, 217, 45, 186, 5, 216, 239, 181, 74, 157, 201, 163, 2, 17, 0, 0, 0, 2, 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: