Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc80bb714b85e3d0b9287ef55d0387bb57b51604da4b74da32445ac6724634c

Tx prefix hash: d7b171faedd13a6bd6a12a1b99d87737866b7873fa77155cdcb559616e2d3c5c
Tx public key: 700d64d122e4fea3e01a2a48f0a581081ba221f00e92979dc68be07283b38ad6
Timestamp: 1674180844 Timestamp [UCT]: 2023-01-20 02:14:04 Age [y:d:h:m:s]: 02:001:06:38:28
Block: 678556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522749 RingCT/type: yes/0
Extra: 01700d64d122e4fea3e01a2a48f0a581081ba221f00e92979dc68be07283b38ad60211000000015029cbac000000000000000000

1 output(s) for total of 3.464672865000 dcy

stealth address amount amount idx
00: a5f122bcf752e1ee6df916c0a7cac5da30ac41ab60d51da2c5432d13a2d7ba24 3.464672865000 1120443 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": 678566, "vin": [ { "gen": { "height": 678556 } } ], "vout": [ { "amount": 3464672865, "target": { "key": "a5f122bcf752e1ee6df916c0a7cac5da30ac41ab60d51da2c5432d13a2d7ba24" } } ], "extra": [ 1, 112, 13, 100, 209, 34, 228, 254, 163, 224, 26, 42, 72, 240, 165, 129, 8, 27, 162, 33, 240, 14, 146, 151, 157, 198, 139, 224, 114, 131, 179, 138, 214, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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