Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad3ad149434f24c7f848b0e95fe9424f64daefad4e4d40467238105b7cbdba8a

Tx prefix hash: 934faa7f4d0763706ca8196e5a18f9960700e03b5d5d333a7c5a03a160fa0fdd
Tx public key: 3e80565367942d000345034db252d8e29b14cafb77551bd8c41a2165d1b42d3a
Timestamp: 1702149395 Timestamp [UCT]: 2023-12-09 19:16:35 Age [y:d:h:m:s]: 01:336:22:01:56
Block: 909570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499651 RingCT/type: yes/0
Extra: 013e80565367942d000345034db252d8e29b14cafb77551bd8c41a2165d1b42d3a02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6e07707cee9d346f78e74efa9d7955e0493d2c1d18872ffdf185e7e39b64c3 0.600000000000 1366669 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": 909580, "vin": [ { "gen": { "height": 909570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6e07707cee9d346f78e74efa9d7955e0493d2c1d18872ffdf185e7e39b64c3" } } ], "extra": [ 1, 62, 128, 86, 83, 103, 148, 45, 0, 3, 69, 3, 77, 178, 82, 216, 226, 155, 20, 202, 251, 119, 85, 27, 216, 196, 26, 33, 101, 209, 180, 45, 58, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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