Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a96d0a7c0359222ffb1b908e8411cdf92cc0be168c89a624f9bf60ebb9c0de8

Tx prefix hash: 268eaa9681c5cebd70e79d184fbd856cf22798f151a0a64857eebc86d6a86714
Tx public key: fa9f1166adeb52396f5380b0b3c553a095f9125c4714a1c21dfd53172697e597
Timestamp: 1707827686 Timestamp [UCT]: 2024-02-13 12:34:46 Age [y:d:h:m:s]: 00:327:19:48:47
Block: 956645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234693 RingCT/type: yes/0
Extra: 01fa9f1166adeb52396f5380b0b3c553a095f9125c4714a1c21dfd53172697e59702110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f19f7b751575604b4c1037942dc6495b190c31bb07c83e1499bd6e9a476ec2a4 0.600000000000 1415955 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": 956655, "vin": [ { "gen": { "height": 956645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f19f7b751575604b4c1037942dc6495b190c31bb07c83e1499bd6e9a476ec2a4" } } ], "extra": [ 1, 250, 159, 17, 102, 173, 235, 82, 57, 111, 83, 128, 176, 179, 197, 83, 160, 149, 249, 18, 92, 71, 20, 161, 194, 29, 253, 83, 23, 38, 151, 229, 151, 2, 17, 0, 0, 0, 10, 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