Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2aead9de5178cc29cdd85735bb485b321ed199dfa5802d1b67560721544c54

Tx prefix hash: 862846319286011f4e1a15b897d46a3009db51f9b4b0d92468ea322bd2fa59f4
Tx public key: 85169db88b1c6a1166e1ad354dc0acb3f8084e4c276b5702c3ef0c7fd7c6d96f
Timestamp: 1714465380 Timestamp [UCT]: 2024-04-30 08:23:00 Age [y:d:h:m:s]: 00:344:14:17:04
Block: 1011662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246339 RingCT/type: yes/0
Extra: 0185169db88b1c6a1166e1ad354dc0acb3f8084e4c276b5702c3ef0c7fd7c6d96f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b8454a701e939b437aa3d4cf2f437fd327658724f5b29ae436bbc6317c0dee1 0.600000000000 1473948 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": 1011672, "vin": [ { "gen": { "height": 1011662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b8454a701e939b437aa3d4cf2f437fd327658724f5b29ae436bbc6317c0dee1" } } ], "extra": [ 1, 133, 22, 157, 184, 139, 28, 106, 17, 102, 225, 173, 53, 77, 192, 172, 179, 248, 8, 78, 76, 39, 107, 87, 2, 195, 239, 12, 127, 215, 198, 217, 111, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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