Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3dc9e5f4f793b3302a89699e085d4967f12e81a50d407356d756a2d553f8df

Tx prefix hash: 2e4418a8eae548793ea0090278b5e57992ce898a50d2fe20d9e7ea6dc508f9bf
Tx public key: 5c8bf5219c5e40d1700ab592acf43d3d8207fbc57c8d1cfc7b7945465f61eb9a
Timestamp: 1577523926 Timestamp [UCT]: 2019-12-28 09:05:26 Age [y:d:h:m:s]: 04:338:02:09:42
Block: 33310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130919 RingCT/type: yes/0
Extra: 015c8bf5219c5e40d1700ab592acf43d3d8207fbc57c8d1cfc7b7945465f61eb9a02110000002aac34bf9e000000000000000000

1 output(s) for total of 476.026357059000 dcy

stealth address amount amount idx
00: 4ea22b099976ec2614ce7aca442d3a0105d8e66ccd565e1b45a7bcd6016c3abf 476.026357059000 55741 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": 33320, "vin": [ { "gen": { "height": 33310 } } ], "vout": [ { "amount": 476026357059, "target": { "key": "4ea22b099976ec2614ce7aca442d3a0105d8e66ccd565e1b45a7bcd6016c3abf" } } ], "extra": [ 1, 92, 139, 245, 33, 156, 94, 64, 209, 112, 10, 181, 146, 172, 244, 61, 61, 130, 7, 251, 197, 124, 141, 28, 252, 123, 121, 69, 70, 95, 97, 235, 154, 2, 17, 0, 0, 0, 42, 172, 52, 191, 158, 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