Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aba9cdf1ffe94095aa630a1bc93b044dc8e91477da0f4f7deb6414343c517d5

Tx prefix hash: 3a4a2bfcf75af7e001e2dcf9a4553beebc3f02fbe12be5c82c456ae997dfe5fa
Tx public key: baa38717b30ec1908304953f6169ead076ef65305159947ad3891da3d5f91a39
Timestamp: 1588733006 Timestamp [UCT]: 2020-05-06 02:43:26 Age [y:d:h:m:s]: 04:274:19:01:57
Block: 98580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112901 RingCT/type: yes/0
Extra: 01baa38717b30ec1908304953f6169ead076ef65305159947ad3891da3d5f91a390211000000028a2ee0d9000000000000000000

1 output(s) for total of 289.310570358000 dcy

stealth address amount amount idx
00: 40829f272f5e7bcbdf52e8faf8e5bcb06b93b4965b2935402839853c535229d0 289.310570358000 174266 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": 98590, "vin": [ { "gen": { "height": 98580 } } ], "vout": [ { "amount": 289310570358, "target": { "key": "40829f272f5e7bcbdf52e8faf8e5bcb06b93b4965b2935402839853c535229d0" } } ], "extra": [ 1, 186, 163, 135, 23, 179, 14, 193, 144, 131, 4, 149, 63, 97, 105, 234, 208, 118, 239, 101, 48, 81, 89, 148, 122, 211, 137, 29, 163, 213, 249, 26, 57, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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