Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 783a42612478654b16d7d514289ba144f9b98f3fab692e19d230b49338093f5c

Tx prefix hash: ba7691104d346f8574c9e6bd2a1443407adb3918b87afe74c8fb1f94522b083d
Tx public key: e685bce7f6e002449adc0ef77bc751e33dcadaea7bfe2c13b4194cb80b76b251
Timestamp: 1714822582 Timestamp [UCT]: 2024-05-04 11:36:22 Age [y:d:h:m:s]: 00:341:09:45:21
Block: 1014636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244042 RingCT/type: yes/0
Extra: 01e685bce7f6e002449adc0ef77bc751e33dcadaea7bfe2c13b4194cb80b76b25102110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dadbced78c9ccf938d0b2b64249d417e7a6aa8981fef61f628970abbd1c7901 0.600000000000 1477781 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": 1014646, "vin": [ { "gen": { "height": 1014636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dadbced78c9ccf938d0b2b64249d417e7a6aa8981fef61f628970abbd1c7901" } } ], "extra": [ 1, 230, 133, 188, 231, 246, 224, 2, 68, 154, 220, 14, 247, 123, 199, 81, 227, 61, 202, 218, 234, 123, 254, 44, 19, 180, 25, 76, 184, 11, 118, 178, 81, 2, 17, 0, 0, 0, 13, 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