Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c589b5f360ef78d4e8c972d738bbf8824a023b44ea4b85e9e0fda9370b1af632

Tx prefix hash: c1e483b5f8b2c466bd0ea3370ecd9a96bd4a4570b646410aef13279458e6b22c
Tx public key: cc6eb4851c7f3952672805373b001b1f7e734757df241ff03fbf6f75e4133ab1
Timestamp: 1681653418 Timestamp [UCT]: 2023-04-16 13:56:58 Age [y:d:h:m:s]: 01:362:02:04:57
Block: 739879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520072 RingCT/type: yes/0
Extra: 01cc6eb4851c7f3952672805373b001b1f7e734757df241ff03fbf6f75e4133ab10211000000055029cbac000000000000000000

1 output(s) for total of 2.170071047000 dcy

stealth address amount amount idx
00: b38b04e5ec9646c7051a83de25074adb060caa33dc4404c5be3d3e231f7af48b 2.170071047000 1186758 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": 739889, "vin": [ { "gen": { "height": 739879 } } ], "vout": [ { "amount": 2170071047, "target": { "key": "b38b04e5ec9646c7051a83de25074adb060caa33dc4404c5be3d3e231f7af48b" } } ], "extra": [ 1, 204, 110, 180, 133, 28, 127, 57, 82, 103, 40, 5, 55, 59, 0, 27, 31, 126, 115, 71, 87, 223, 36, 31, 240, 63, 191, 111, 117, 228, 19, 58, 177, 2, 17, 0, 0, 0, 5, 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