Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 327b77ef579b0fe7229e827dfd3fd597fe8ac94f424d05928904f2edd6d48b0f

Tx prefix hash: 37ca74e22036507987e78651d80e681c88d96f7f7aa0a5ce5edaef560315b56a
Tx public key: 14d36e962eebbe2e1005514711f040adc56bdbae49dab5ba63c0b39fc336f26e
Timestamp: 1700579203 Timestamp [UCT]: 2023-11-21 15:06:43 Age [y:d:h:m:s]: 01:134:10:36:16
Block: 896539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357255 RingCT/type: yes/0
Extra: 0114d36e962eebbe2e1005514711f040adc56bdbae49dab5ba63c0b39fc336f26e021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.656740970000 dcy

stealth address amount amount idx
00: b2038f70e6e73e2a1d5ec0364856cb8f900e23adb1754335bd834a39cb6351d3 0.656740970000 1352866 of 0

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": 896549, "vin": [ { "gen": { "height": 896539 } } ], "vout": [ { "amount": 656740970, "target": { "key": "b2038f70e6e73e2a1d5ec0364856cb8f900e23adb1754335bd834a39cb6351d3" } } ], "extra": [ 1, 20, 211, 110, 150, 46, 235, 190, 46, 16, 5, 81, 71, 17, 240, 64, 173, 197, 107, 219, 174, 73, 218, 181, 186, 99, 192, 179, 159, 195, 54, 242, 110, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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