Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3baa8f047577cf35943bfd7807e64215c17a07758be904bcf79f3e24a3b693e

Tx prefix hash: 4c4fc477c782c4650c72a5a276acea652f5573dc2677146afdcdadc787bde222
Tx public key: 17c6f252001f71ed09b424f811ac80ef0996ad7a9bdcee88ea07bfce82599612
Timestamp: 1772477164 Timestamp [UTC]: 2026-03-02 18:46:04 Age [y:d:h:m:s]: 00:263:20:10:07
Block: 1489254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194230 RingCT/type: yes/0
Extra: 0117c6f252001f71ed09b424f811ac80ef0996ad7a9bdcee88ea07bfce82599612021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d9c87c9f1bb9b2b026f45c8381d890be4bfda69a21d6b6e3edd7c428ad99a81 0.000600000000 1978742 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": 1489264, "vin": [ { "gen": { "height": 1489254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d9c87c9f1bb9b2b026f45c8381d890be4bfda69a21d6b6e3edd7c428ad99a81" } } ], "extra": [ 1, 23, 198, 242, 82, 0, 31, 113, 237, 9, 180, 36, 248, 17, 172, 128, 239, 9, 150, 173, 122, 155, 220, 238, 136, 234, 7, 191, 206, 130, 89, 150, 18, 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: