Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce5f92e5bcced13e644dfc3262e7596208804d5318b3d334e585d84523418b1

Tx prefix hash: 79ec654d4a43557025f7d24b05aafbb522010dfd42011e893b9c273e56ec1308
Tx public key: 74a11c785d7af0cd0e418ca80e40c1bbb1a7a93b6b5ce6096ef94752258bd1fa
Timestamp: 1722098872 Timestamp [UCT]: 2024-07-27 16:47:52 Age [y:d:h:m:s]: 00:247:03:08:41
Block: 1074956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176529 RingCT/type: yes/0
Extra: 0174a11c785d7af0cd0e418ca80e40c1bbb1a7a93b6b5ce6096ef94752258bd1fa021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6b6994facdc53e0d7da278441a1bcf999a3ec2167e0138cd9add2b4282772f1 0.600000000000 1547475 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": 1074966, "vin": [ { "gen": { "height": 1074956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6b6994facdc53e0d7da278441a1bcf999a3ec2167e0138cd9add2b4282772f1" } } ], "extra": [ 1, 116, 161, 28, 120, 93, 122, 240, 205, 14, 65, 140, 168, 14, 64, 193, 187, 177, 167, 169, 59, 107, 92, 230, 9, 110, 249, 71, 82, 37, 139, 209, 250, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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