Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342d70b75581074d888ba3d8f12fc878259dd300a04647e8bdb303fd0a82c2da

Tx prefix hash: 646e791048ae17420f00c85ab2af0c763348ca6d3d0f1dee60fd01caa1844f16
Tx public key: a44fef319a3f7bc3fa47b12c95b5d013e4b7f7ab2ac06fd5852ef18ad729b1b1
Timestamp: 1640797338 Timestamp [UCT]: 2021-12-29 17:02:18 Age [y:d:h:m:s]: 03:075:19:21:34
Block: 406164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832964 RingCT/type: yes/0
Extra: 01a44fef319a3f7bc3fa47b12c95b5d013e4b7f7ab2ac06fd5852ef18ad729b1b10211000000011a5e7f5d000000000000000000

1 output(s) for total of 27.682824771000 dcy

stealth address amount amount idx
00: 83e39b13dfb552df9c5a55a89932cc8ba0000510b85b77ea3e62098c5704f72d 27.682824771000 806898 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": 406174, "vin": [ { "gen": { "height": 406164 } } ], "vout": [ { "amount": 27682824771, "target": { "key": "83e39b13dfb552df9c5a55a89932cc8ba0000510b85b77ea3e62098c5704f72d" } } ], "extra": [ 1, 164, 79, 239, 49, 154, 63, 123, 195, 250, 71, 177, 44, 149, 181, 208, 19, 228, 183, 247, 171, 42, 192, 111, 213, 133, 46, 241, 138, 215, 41, 177, 177, 2, 17, 0, 0, 0, 1, 26, 94, 127, 93, 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