Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9692fe64b799f4c7849d78462b65b883c68fb8c2bae5d1b69f5ee6788209cc04

Tx prefix hash: 0c81973bdc0017859dcca400ecb42be60b4cfa41f6562bcbee9763fcb2729d1c
Tx public key: 8c7e258f663f0094d523244a497496d52e6eecf3a0cbf3a94f66b6702e2b4dd0
Timestamp: 1720038415 Timestamp [UCT]: 2024-07-03 20:26:55 Age [y:d:h:m:s]: 01:128:07:57:39
Block: 1057864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350254 RingCT/type: yes/0
Extra: 018c7e258f663f0094d523244a497496d52e6eecf3a0cbf3a94f66b6702e2b4dd00211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f9dd3119f99edd5d3d3e2353e074c090b40a0506ff85e24449542b12e075b4c 0.600000000000 1528307 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": 1057874, "vin": [ { "gen": { "height": 1057864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f9dd3119f99edd5d3d3e2353e074c090b40a0506ff85e24449542b12e075b4c" } } ], "extra": [ 1, 140, 126, 37, 143, 102, 63, 0, 148, 213, 35, 36, 74, 73, 116, 150, 213, 46, 110, 236, 243, 160, 203, 243, 169, 79, 102, 182, 112, 46, 43, 77, 208, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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