Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f797c2b045316dd6056af1dfcef11cde351e86818ea054febbcca7dbda1d66f6

Tx prefix hash: 84fa6bb24661a1c85c95b5c6f8e5221487b6969e6fd620377aa2a9b24762014e
Tx public key: 2cdf55016c23a9aab0a4bee8d474bcd72c2ad0830a10d46a67d8d05b63a3002f
Timestamp: 1733487577 Timestamp [UCT]: 2024-12-06 12:19:37 Age [y:d:h:m:s]: 00:157:20:56:15
Block: 1169268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112662 RingCT/type: yes/0
Extra: 012cdf55016c23a9aab0a4bee8d474bcd72c2ad0830a10d46a67d8d05b63a3002f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d891bc761fb14ee0ebbb1ae645d54f392b51261b1c36e5bc8718bb08039798eb 0.600000000000 1654983 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": 1169278, "vin": [ { "gen": { "height": 1169268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d891bc761fb14ee0ebbb1ae645d54f392b51261b1c36e5bc8718bb08039798eb" } } ], "extra": [ 1, 44, 223, 85, 1, 108, 35, 169, 170, 176, 164, 190, 232, 212, 116, 188, 215, 44, 42, 208, 131, 10, 16, 212, 106, 103, 216, 208, 91, 99, 163, 0, 47, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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