Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e2627fa4163c0f4c0de6c4e2c2e17e15d44d415ec2425a14dbe995df488577b

Tx prefix hash: 34c07c7bee027ce07ff70fa506ae3bf01bc58a5763b015987ccdaa4afd4adc87
Tx public key: 368777d503f2f467e28e75cd7757e58b5fa38797ba469bd04fd1ea2400e3015a
Timestamp: 1703769003 Timestamp [UCT]: 2023-12-28 13:10:03 Age [y:d:h:m:s]: 01:340:13:41:17
Block: 922990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502276 RingCT/type: yes/0
Extra: 01368777d503f2f467e28e75cd7757e58b5fa38797ba469bd04fd1ea2400e3015a021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9bbe7fe55e7f291239bcf4346e6a97ff2fb7f29ac6fa1bd09dcc4a8f7fb264 0.600000000000 1380696 of 15

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": 923000, "vin": [ { "gen": { "height": 922990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9bbe7fe55e7f291239bcf4346e6a97ff2fb7f29ac6fa1bd09dcc4a8f7fb264" } } ], "extra": [ 1, 54, 135, 119, 213, 3, 242, 244, 103, 226, 142, 117, 205, 119, 87, 229, 139, 95, 163, 135, 151, 186, 70, 155, 208, 79, 209, 234, 36, 0, 227, 1, 90, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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