Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28bef59c3a37e8eb4068402504c3c0eaa6cfbeeb8a2e5367baed4127dc7dc32

Tx prefix hash: 446c769f6bd1052027e879350cc08df8916f14914986e238846fd5444e8edc05
Tx public key: 285d1eb75b87206035c5dddc2d798d48bc6f7c878417ae7d74124c80c3a96659
Timestamp: 1717736391 Timestamp [UCT]: 2024-06-07 04:59:51 Age [y:d:h:m:s]: 00:230:08:14:28
Block: 1038789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164799 RingCT/type: yes/0
Extra: 01285d1eb75b87206035c5dddc2d798d48bc6f7c878417ae7d74124c80c3a9665902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f52587d8d1f562ce6f11a8bd54b6725e584246ad8e744b28cdfafca03cd149 0.600000000000 1507350 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": 1038799, "vin": [ { "gen": { "height": 1038789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f52587d8d1f562ce6f11a8bd54b6725e584246ad8e744b28cdfafca03cd149" } } ], "extra": [ 1, 40, 93, 30, 183, 91, 135, 32, 96, 53, 197, 221, 220, 45, 121, 141, 72, 188, 111, 124, 135, 132, 23, 174, 125, 116, 18, 76, 128, 195, 169, 102, 89, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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