Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e97ad12457c0a60987b67c5e31bb46f8b7ed23b4b18501f6d941953be7c7d22d

Tx prefix hash: ebb7b479ef53c2041f68e22c2fedfb7a1ebd7f1284f3455b176e055a06ad59cd
Tx public key: 20d07b40717d0386372baa6b639192e58352b26275bae5f55887afc14c7e327b
Timestamp: 1714107674 Timestamp [UCT]: 2024-04-26 05:01:14 Age [y:d:h:m:s]: 00:203:05:27:19
Block: 1008701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145485 RingCT/type: yes/0
Extra: 0120d07b40717d0386372baa6b639192e58352b26275bae5f55887afc14c7e327b02110000000218ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7990883ed3a1c8d0a63db2dd80472fa5a4a65a2e0f1f907ab734d1110ff3bda3 0.600000000000 1470177 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": 1008711, "vin": [ { "gen": { "height": 1008701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7990883ed3a1c8d0a63db2dd80472fa5a4a65a2e0f1f907ab734d1110ff3bda3" } } ], "extra": [ 1, 32, 208, 123, 64, 113, 125, 3, 134, 55, 43, 170, 107, 99, 145, 146, 229, 131, 82, 178, 98, 117, 186, 229, 245, 88, 135, 175, 193, 76, 126, 50, 123, 2, 17, 0, 0, 0, 2, 24, 236, 144, 96, 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