Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc088242aac5e61324b808525fe48e50638bcb217e73842ffedcc2f840c8a957

Tx prefix hash: 6f98f5f6268379ad24141566e6f2611c0f0da77777e59d8be29f063c9781e750
Tx public key: 0ad65c9dd7d4ecb0019adcb343e5a708f92aef0ca30a3e8ce7b95eb6ab98a68c
Timestamp: 1771238410 Timestamp [UTC]: 2026-02-16 10:40:10 Age [y:d:h:m:s]: 00:273:16:00:26
Block: 1478993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201092 RingCT/type: yes/0
Extra: 010ad65c9dd7d4ecb0019adcb343e5a708f92aef0ca30a3e8ce7b95eb6ab98a68c021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c49940dbf4eb784188edef750d2d64e37f543a85a13cc45be50f237ed3aa80f4 0.000600000000 1968327 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": 1479003, "vin": [ { "gen": { "height": 1478993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49940dbf4eb784188edef750d2d64e37f543a85a13cc45be50f237ed3aa80f4" } } ], "extra": [ 1, 10, 214, 92, 157, 215, 212, 236, 176, 1, 154, 220, 179, 67, 229, 167, 8, 249, 42, 239, 12, 163, 10, 62, 140, 231, 185, 94, 182, 171, 152, 166, 140, 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: