Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef364f81129e4531cb2d574bea3c832ceaeabdaefa64db5ec28f36b71f7a45e4

Tx prefix hash: 19791920b665d675e8ffdf8d0dccf89bfbe666d57ef0c309df62a536e1c0095a
Tx public key: 36f9954d9a38979e1e549e7fe8c2278f4dae24f7ab6633f061579b0715c90de5
Timestamp: 1713696846 Timestamp [UCT]: 2024-04-21 10:54:06 Age [y:d:h:m:s]: 00:200:13:56:49
Block: 1005296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143596 RingCT/type: yes/0
Extra: 0136f9954d9a38979e1e549e7fe8c2278f4dae24f7ab6633f061579b0715c90de50211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7e371c91ba0ee69bd1ebcde489fa8ef8b2dfd6d0084f7caa262cc9621b9c0e 0.600000000000 1465882 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": 1005306, "vin": [ { "gen": { "height": 1005296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7e371c91ba0ee69bd1ebcde489fa8ef8b2dfd6d0084f7caa262cc9621b9c0e" } } ], "extra": [ 1, 54, 249, 149, 77, 154, 56, 151, 158, 30, 84, 158, 127, 232, 194, 39, 143, 77, 174, 36, 247, 171, 102, 51, 240, 97, 87, 155, 7, 21, 201, 13, 229, 2, 17, 0, 0, 0, 5, 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