Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b4c31598dcfcac66127caf3165c5f9574af579438f9ff3a9dfd53272d7c2a4c

Tx prefix hash: 97d38436b87939c3c5a013f4025c29b82d66456ad998ef54acc5ac15d42722d7
Tx public key: 495ba7132471939a09cb7eb91e3d75a41f9862e84581a8c2cac601d8fa794534
Timestamp: 1727811648 Timestamp [UCT]: 2024-10-01 19:40:48 Age [y:d:h:m:s]: 00:080:16:35:27
Block: 1122327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57704 RingCT/type: yes/0
Extra: 01495ba7132471939a09cb7eb91e3d75a41f9862e84581a8c2cac601d8fa794534021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69293b19c74f026911bf6efc74b2a9a984c33cc0e6c08b139afc2c890e987207 0.600000000000 1604746 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": 1122337, "vin": [ { "gen": { "height": 1122327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69293b19c74f026911bf6efc74b2a9a984c33cc0e6c08b139afc2c890e987207" } } ], "extra": [ 1, 73, 91, 167, 19, 36, 113, 147, 154, 9, 203, 126, 185, 30, 61, 117, 164, 31, 152, 98, 232, 69, 129, 168, 194, 202, 198, 1, 216, 250, 121, 69, 52, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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