Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1c326851c85add8a252ccf0e1ce96b01e1296e61709110b3678b4f7d17e3a7

Tx prefix hash: 2c1763385905dd5c7b9c767261df9f89ee6301587418d4467659555223ca6e95
Tx public key: 2653b46a763293f2873c0aaae5a7e87c6a489e7c01d905c62f12f77f02c0d1ab
Timestamp: 1593491023 Timestamp [UCT]: 2020-06-30 04:23:43 Age [y:d:h:m:s]: 04:142:09:28:05
Block: 112393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1044030 RingCT/type: yes/0
Extra: 012653b46a763293f2873c0aaae5a7e87c6a489e7c01d905c62f12f77f02c0d1ab02110000002946a11e8a000000000000000000

1 output(s) for total of 260.373079111000 dcy

stealth address amount amount idx
00: 9e351882ada834a19793fc8c93b3dc8f0fc42defc7bf68a32c7939a2d42f9ab8 260.373079111000 193744 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": 112403, "vin": [ { "gen": { "height": 112393 } } ], "vout": [ { "amount": 260373079111, "target": { "key": "9e351882ada834a19793fc8c93b3dc8f0fc42defc7bf68a32c7939a2d42f9ab8" } } ], "extra": [ 1, 38, 83, 180, 106, 118, 50, 147, 242, 135, 60, 10, 170, 229, 167, 232, 124, 106, 72, 158, 124, 1, 217, 5, 198, 47, 18, 247, 127, 2, 192, 209, 171, 2, 17, 0, 0, 0, 41, 70, 161, 30, 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