Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7744ad13a8a4cfbb772b6eb49b11bdb0453dc451db8ee2394e05e5992540236f

Tx prefix hash: 443efc7caf407d0d41839f733bcaf7ed36ce1f9cd42a9c061739ae1df8a480c2
Tx public key: 8320856bad60c62a76e3442cf30fdb1c7a2a3e53eb6fb3c60d359ba793979f54
Timestamp: 1707165594 Timestamp [UCT]: 2024-02-05 20:39:54 Age [y:d:h:m:s]: 01:054:15:53:22
Block: 951144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300123 RingCT/type: yes/0
Extra: 018320856bad60c62a76e3442cf30fdb1c7a2a3e53eb6fb3c60d359ba793979f540211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee20e2763d67f728c8f670bd19122401462f58d54b84ce4f568071a1e08745f9 0.600000000000 1409870 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": 951154, "vin": [ { "gen": { "height": 951144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee20e2763d67f728c8f670bd19122401462f58d54b84ce4f568071a1e08745f9" } } ], "extra": [ 1, 131, 32, 133, 107, 173, 96, 198, 42, 118, 227, 68, 44, 243, 15, 219, 28, 122, 42, 62, 83, 235, 111, 179, 198, 13, 53, 155, 167, 147, 151, 159, 84, 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