Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ee87bea4cd4462e238d9f929f1ef95d9ef6d40d3a0f0b45ad3ec42a2ba83d4f

Tx prefix hash: c4636d0de7e4645c816c8a2831df914f3dee966a5f3874f8a5366a88628ee1dc
Tx public key: 2463520f1b2a58719e84858fc3d715c137f1e727ac713813425af7388019e519
Timestamp: 1705437989 Timestamp [UCT]: 2024-01-16 20:46:29 Age [y:d:h:m:s]: 01:097:00:34:45
Block: 936815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330434 RingCT/type: yes/0
Extra: 012463520f1b2a58719e84858fc3d715c137f1e727ac713813425af7388019e5190211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d6cfe063622b5d5b20235a8ef74c0894659327999668a5fe51fd88f194a3747 0.600000000000 1394855 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": 936825, "vin": [ { "gen": { "height": 936815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d6cfe063622b5d5b20235a8ef74c0894659327999668a5fe51fd88f194a3747" } } ], "extra": [ 1, 36, 99, 82, 15, 27, 42, 88, 113, 158, 132, 133, 143, 195, 215, 21, 193, 55, 241, 231, 39, 172, 113, 56, 19, 66, 90, 247, 56, 128, 25, 229, 25, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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