Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a365d1c52f70f5bbdee11c7d754896c4673db872fb8c15be416bab9983f34739

Tx prefix hash: 7fd77f5d2d67286749c0e0c9824129f44bd8ba84ba4373252aab36456fa3c314
Tx public key: e827a701701f7a1e8c27a5cdf5de68669fa6c0051ee826177e2e4e1fa5f54489
Timestamp: 1738341800 Timestamp [UCT]: 2025-01-31 16:43:20 Age [y:d:h:m:s]: 00:293:11:33:33
Block: 1209192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207505 RingCT/type: yes/0
Extra: 01e827a701701f7a1e8c27a5cdf5de68669fa6c0051ee826177e2e4e1fa5f544890211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fd1f14feed8cb373e707d25ecc27f0df680c9c5a155afda270b82aa7bdf02e9 0.600000000000 1695933 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": 1209202, "vin": [ { "gen": { "height": 1209192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fd1f14feed8cb373e707d25ecc27f0df680c9c5a155afda270b82aa7bdf02e9" } } ], "extra": [ 1, 232, 39, 167, 1, 112, 31, 122, 30, 140, 39, 165, 205, 245, 222, 104, 102, 159, 166, 192, 5, 30, 232, 38, 23, 126, 46, 78, 31, 165, 245, 68, 137, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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