Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d094cf235bf6b655be48f3c4e8965de711ab646008ed80d5ad6559f3bf9670e

Tx prefix hash: b886808b8023d8327f4206ea2700d5da1e10d35637baa910ef21f948150dc89a
Tx public key: e26681fdcb2fc337a83ae9224bd268e5e30eea20aa2202d9c9b25b5a83b7e88c
Timestamp: 1617739901 Timestamp [UCT]: 2021-04-06 20:11:41 Age [y:d:h:m:s]: 03:228:05:01:14
Block: 234579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 922912 RingCT/type: yes/0
Extra: 01e26681fdcb2fc337a83ae9224bd268e5e30eea20aa2202d9c9b25b5a83b7e88c0211000000013634f08d000000000000000000

1 output(s) for total of 102.504508959000 dcy

stealth address amount amount idx
00: 5a9eba5fd8827c6f4b0d3b0d15faf44f5149f741f13c4af0d7a6757877996359 102.504508959000 487065 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": 234589, "vin": [ { "gen": { "height": 234579 } } ], "vout": [ { "amount": 102504508959, "target": { "key": "5a9eba5fd8827c6f4b0d3b0d15faf44f5149f741f13c4af0d7a6757877996359" } } ], "extra": [ 1, 226, 102, 129, 253, 203, 47, 195, 55, 168, 58, 233, 34, 75, 210, 104, 229, 227, 14, 234, 32, 170, 34, 2, 217, 201, 178, 91, 90, 131, 183, 232, 140, 2, 17, 0, 0, 0, 1, 54, 52, 240, 141, 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