Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e596717e9216b328f1614deabd3fbfbaf1fad25a693f03aeae3132a992acbf9

Tx prefix hash: 831bb321072d5746d8996099821f5e919746c429ddfe445301533e8800405bd9
Tx public key: 365d89f3c868f6cb056880ef2c4b9e245f195bc76ea5eccf1598f3f63f6aaf34
Timestamp: 1719094089 Timestamp [UCT]: 2024-06-22 22:08:09 Age [y:d:h:m:s]: 00:281:21:39:01
Block: 1050026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201454 RingCT/type: yes/0
Extra: 01365d89f3c868f6cb056880ef2c4b9e245f195bc76ea5eccf1598f3f63f6aaf3402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79b073de5f98a6166abe29b2c88d997ebc7adbf3ed7ac74396e9f25684717bc 0.600000000000 1520173 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": 1050036, "vin": [ { "gen": { "height": 1050026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79b073de5f98a6166abe29b2c88d997ebc7adbf3ed7ac74396e9f25684717bc" } } ], "extra": [ 1, 54, 93, 137, 243, 200, 104, 246, 203, 5, 104, 128, 239, 44, 75, 158, 36, 95, 25, 91, 199, 110, 165, 236, 207, 21, 152, 243, 246, 63, 106, 175, 52, 2, 17, 0, 0, 0, 1, 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