Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282e0479b3533ce18b10254227b19bf401d89027d2c7308d72b5eba9a74a9e68

Tx prefix hash: 2f6021abf03aaa56ded49d7d4e846bc1bce111762607a231da2b81b58a93fe18
Tx public key: d7c16a974f834e9b3f0f5c621edc0cdd689e99b50c50ccff4455465d4748a837
Timestamp: 1726887082 Timestamp [UCT]: 2024-09-21 02:51:22 Age [y:d:h:m:s]: 01:050:04:20:35
Block: 1114654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294271 RingCT/type: yes/0
Extra: 01d7c16a974f834e9b3f0f5c621edc0cdd689e99b50c50ccff4455465d4748a837021100000002bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62d07354adecb84689afece5ae3415a292c8c6e7eb8d1ddb9424aaec08ac648c 0.600000000000 1594511 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": 1114664, "vin": [ { "gen": { "height": 1114654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62d07354adecb84689afece5ae3415a292c8c6e7eb8d1ddb9424aaec08ac648c" } } ], "extra": [ 1, 215, 193, 106, 151, 79, 131, 78, 155, 63, 15, 92, 98, 30, 220, 12, 221, 104, 158, 153, 181, 12, 80, 204, 255, 68, 85, 70, 93, 71, 72, 168, 55, 2, 17, 0, 0, 0, 2, 189, 175, 233, 204, 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