Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdc6b86e5607fa6bf230d3273e0abc03bbc3eb71fccab73ed1a038a200d4458

Tx prefix hash: eee29a8f0b5f743a7d16d662d41db5c9c33aead924357df2ea5d39ba9623d82e
Tx public key: bb05fd68d07ddd3e83f5894f6918e565e6ce64d5e97966f918a70d450f11c1a8
Timestamp: 1770968286 Timestamp [UTC]: 2026-02-13 07:38:06 Age [y:d:h:m:s]: 00:001:05:13:04
Block: 1476787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 844 RingCT/type: yes/0
Extra: 01bb05fd68d07ddd3e83f5894f6918e565e6ce64d5e97966f918a70d450f11c1a8020886cd253c78869d2a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80ad84c8d1c4e2a0e798ca61ee8649ffd7b36ed1369642fd0aa9ee533e6df03e 0.000600000000 1966097 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": 1476797, "vin": [ { "gen": { "height": 1476787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ad84c8d1c4e2a0e798ca61ee8649ffd7b36ed1369642fd0aa9ee533e6df03e" } } ], "extra": [ 1, 187, 5, 253, 104, 208, 125, 221, 62, 131, 245, 137, 79, 105, 24, 229, 101, 230, 206, 100, 213, 233, 121, 102, 249, 24, 167, 13, 69, 15, 17, 193, 168, 2, 8, 134, 205, 37, 60, 120, 134, 157, 42 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369