Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe70acf2d768c6c3305b6382ee7ca383d3cb85094add40590304297259d4720

Tx prefix hash: 05f49d31196eaa1d84a30750034dc63b3c2f7d9fa46b8a81a68f53b316a71ddd
Tx public key: 1185f7e6f576ad7bb7cee378d749cfbfb8d1398c7835afd178c073eef83883b9
Timestamp: 1749193512 Timestamp [UCT]: 2025-06-06 07:05:12 Age [y:d:h:m:s]: 00:164:15:57:56
Block: 1299037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115367 RingCT/type: yes/0
Extra: 011185f7e6f576ad7bb7cee378d749cfbfb8d1398c7835afd178c073eef83883b902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd2060b1b53a2e9d62d3b04fbb362dcb83bc1dd4d3be17518355e99efa58fcf9 0.600000000000 1786572 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 dinasty-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": 1299047, "vin": [ { "gen": { "height": 1299037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd2060b1b53a2e9d62d3b04fbb362dcb83bc1dd4d3be17518355e99efa58fcf9" } } ], "extra": [ 1, 17, 133, 247, 230, 245, 118, 173, 123, 183, 206, 227, 120, 215, 73, 207, 191, 184, 209, 57, 140, 120, 53, 175, 209, 120, 192, 115, 238, 248, 56, 131, 185, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8