Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d75d7424b9db08af4a0f2db22a1e1d295bb661b1332694e5958c33d2341c90c2

Tx prefix hash: 4a598468f45972307a5411ca38dd97ddb3809d5ab83f3a4a7bd9d1eae1dee19c
Tx public key: dfdeddf8f2cd44cb235fda22f5ae883be1e27cba2615d5d4681abe82d583cb52
Timestamp: 1707794396 Timestamp [UCT]: 2024-02-13 03:19:56 Age [y:d:h:m:s]: 01:053:08:12:17
Block: 956362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299159 RingCT/type: yes/0
Extra: 01dfdeddf8f2cd44cb235fda22f5ae883be1e27cba2615d5d4681abe82d583cb5202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18101c98f4ca0d9541d2cb37afcba14171164153bb7a70ede46dff067bcd33f 0.600000000000 1415666 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": 956372, "vin": [ { "gen": { "height": 956362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18101c98f4ca0d9541d2cb37afcba14171164153bb7a70ede46dff067bcd33f" } } ], "extra": [ 1, 223, 222, 221, 248, 242, 205, 68, 203, 35, 95, 218, 34, 245, 174, 136, 59, 225, 226, 124, 186, 38, 21, 213, 212, 104, 26, 190, 130, 213, 131, 203, 82, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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