Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f5b9f29eccfbbe535e4656d9dc18a260d6ffc306db305bd05efb3c438383aa

Tx prefix hash: ab518f3568b4225cf383a6bd48848c6d1aac046667640c4cbc21f7bc899f7d7a
Tx public key: 6d63b8840d2f95611572a8bc4e310be5ef67c31d627c64f426e9259b713f8e8f
Timestamp: 1771221378 Timestamp [UTC]: 2026-02-16 05:56:18 Age [y:d:h:m:s]: 00:273:21:03:24
Block: 1478856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201239 RingCT/type: yes/0
Extra: 016d63b8840d2f95611572a8bc4e310be5ef67c31d627c64f426e9259b713f8e8f021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0ae1cdd4d9798c0940d58ecd0e0072607a0b869bdcc16251bcbf02a92455f6cc 0.000600000000 1968188 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": 1478866, "vin": [ { "gen": { "height": 1478856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae1cdd4d9798c0940d58ecd0e0072607a0b869bdcc16251bcbf02a92455f6cc" } } ], "extra": [ 1, 109, 99, 184, 132, 13, 47, 149, 97, 21, 114, 168, 188, 78, 49, 11, 229, 239, 103, 195, 29, 98, 124, 100, 244, 38, 233, 37, 155, 113, 63, 142, 143, 2, 17, 0, 0, 0, 1, 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: