Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aafcfa366aaddd73c7a4dc0675aafd40e0e4e432d9032718faafe6620a6c3685

Tx prefix hash: 919654647d5d65f9e2fdf2bdc9506fda6aa9d7062fb7773bd3a41f877c745833
Tx public key: e88fd942d40dc52a52a05e344131e4dea33b70bebc6eed8c9fa1cde51ad67256
Timestamp: 1712983101 Timestamp [UCT]: 2024-04-13 04:38:21 Age [y:d:h:m:s]: 00:317:07:45:57
Block: 999356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226855 RingCT/type: yes/0
Extra: 01e88fd942d40dc52a52a05e344131e4dea33b70bebc6eed8c9fa1cde51ad672560211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28be8a9abc1092cda99362cf3bb445c266d22527e28707248c3a4b64294cac9 0.600000000000 1459834 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": 999366, "vin": [ { "gen": { "height": 999356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28be8a9abc1092cda99362cf3bb445c266d22527e28707248c3a4b64294cac9" } } ], "extra": [ 1, 232, 143, 217, 66, 212, 13, 197, 42, 82, 160, 94, 52, 65, 49, 228, 222, 163, 59, 112, 190, 188, 110, 237, 140, 159, 161, 205, 229, 26, 214, 114, 86, 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