Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2639be64bf674dc95620d9e21ec8a70f781796785dfc77be54a3ae24c9a5091d

Tx prefix hash: e346d6228633e9cd225cdd9e68429dac88d276497f7a79a7c18200fdd78dd0db
Tx public key: 18ec4ec4c07212e7cb64b18a30377e8e03f4abb371f0a0ff4e6f234180d49c65
Timestamp: 1704325744 Timestamp [UCT]: 2024-01-03 23:49:04 Age [y:d:h:m:s]: 01:126:14:27:11
Block: 927615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351593 RingCT/type: yes/0
Extra: 0118ec4ec4c07212e7cb64b18a30377e8e03f4abb371f0a0ff4e6f234180d49c6502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59287761fa07e0a587788623c1339f807513ebb216ca98ac05e836248eeea8f0 0.600000000000 1385451 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": 927625, "vin": [ { "gen": { "height": 927615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59287761fa07e0a587788623c1339f807513ebb216ca98ac05e836248eeea8f0" } } ], "extra": [ 1, 24, 236, 78, 196, 192, 114, 18, 231, 203, 100, 177, 138, 48, 55, 126, 142, 3, 244, 171, 179, 113, 240, 160, 255, 78, 111, 35, 65, 128, 212, 156, 101, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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