Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5794dfe8864712de88727fa612593c5f3d50561ca95897aa3bbfb501e1c81f76

Tx prefix hash: fee2fc1d7d88b877e6aeb6d4d023d47aa39e57fee8bb70946387708dafd69266
Tx public key: c4b3fbbfafb599f8e4faa1daf729ed65ab64a33dc1435b6976d85d09fa09ddb0
Timestamp: 1658082426 Timestamp [UCT]: 2022-07-17 18:27:06 Age [y:d:h:m:s]: 02:246:04:56:03
Block: 545894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697137 RingCT/type: yes/0
Extra: 01c4b3fbbfafb599f8e4faa1daf729ed65ab64a33dc1435b6976d85d09fa09ddb002110000000cc9067537000000000000000000

1 output(s) for total of 9.532936605000 dcy

stealth address amount amount idx
00: a3ef657a276609018400804a017ade7b9530f1df97e086076da34db12bac10c9 9.532936605000 976843 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": 545904, "vin": [ { "gen": { "height": 545894 } } ], "vout": [ { "amount": 9532936605, "target": { "key": "a3ef657a276609018400804a017ade7b9530f1df97e086076da34db12bac10c9" } } ], "extra": [ 1, 196, 179, 251, 191, 175, 181, 153, 248, 228, 250, 161, 218, 247, 41, 237, 101, 171, 100, 163, 61, 193, 67, 91, 105, 118, 216, 93, 9, 250, 9, 221, 176, 2, 17, 0, 0, 0, 12, 201, 6, 117, 55, 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