Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ccd2b189a2d76fb150b95242f6771f4a88601176f4c9a7e8cd5e5366c887e7

Tx prefix hash: cb31cb80c45dbf232336f6a56486c972637e77738cc5e607e86e77272804a0dd
Tx public key: ef3de803a5afc690c3c3b7695209b3c754f55b9937f9729f6968e86082230738
Timestamp: 1687430669 Timestamp [UCT]: 2023-06-22 10:44:29 Age [y:d:h:m:s]: 01:127:01:36:39
Block: 787789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352183 RingCT/type: yes/0
Extra: 01ef3de803a5afc690c3c3b7695209b3c754f55b9937f9729f6968e8608223073802110000000175e3f0e9000000000000000000

1 output(s) for total of 1.505664337000 dcy

stealth address amount amount idx
00: 33d20c873174d463d924b5bdb45a7ec1aab02314a4ca4ee50a71ad802dd9040b 1.505664337000 1237874 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": 787799, "vin": [ { "gen": { "height": 787789 } } ], "vout": [ { "amount": 1505664337, "target": { "key": "33d20c873174d463d924b5bdb45a7ec1aab02314a4ca4ee50a71ad802dd9040b" } } ], "extra": [ 1, 239, 61, 232, 3, 165, 175, 198, 144, 195, 195, 183, 105, 82, 9, 179, 199, 84, 245, 91, 153, 55, 249, 114, 159, 105, 104, 232, 96, 130, 35, 7, 56, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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