Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569c5ca97915aead6fee161d820afe539134a4c896cb60215c8f448e15dbea86

Tx prefix hash: 6734852edf17eaf0ab267cb0e969377c3cbf195250b4df49c4d004dbe7be2f14
Tx public key: 707e8827f0d6cdf3ffab24d4f6256862208687e88b6d95a81d70b52842c4ef00
Timestamp: 1701898467 Timestamp [UCT]: 2023-12-06 21:34:27 Age [y:d:h:m:s]: 01:336:14:29:12
Block: 907480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499439 RingCT/type: yes/0
Extra: 01707e8827f0d6cdf3ffab24d4f6256862208687e88b6d95a81d70b52842c4ef0002110000000139e1d5d3000000000000000000

1 output(s) for total of 0.604146160000 dcy

stealth address amount amount idx
00: fc97732fcadd9bbab0c48d18dbbe9a001ca435b1b28040b52c6a4253de41ba98 0.604146160000 1364473 of 0

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": 907490, "vin": [ { "gen": { "height": 907480 } } ], "vout": [ { "amount": 604146160, "target": { "key": "fc97732fcadd9bbab0c48d18dbbe9a001ca435b1b28040b52c6a4253de41ba98" } } ], "extra": [ 1, 112, 126, 136, 39, 240, 214, 205, 243, 255, 171, 36, 212, 246, 37, 104, 98, 32, 134, 135, 232, 139, 109, 149, 168, 29, 112, 181, 40, 66, 196, 239, 0, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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