Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6340fe6817fb1d21fcba007d2f91f4c025df4f93d4b10930eb8940948c662eab

Tx prefix hash: aa64b3e3385bd90f791d2da14d28b51af2881c6d9e7dce6fe2916984da7c3706
Tx public key: 8f1d8c1e970ebf73e2ea0b566573e93a0dd740fe7de1e5a09d614af0910df788
Timestamp: 1737857089 Timestamp [UCT]: 2025-01-26 02:04:49 Age [y:d:h:m:s]: 00:146:19:46:23
Block: 1205404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104626 RingCT/type: yes/0
Extra: 018f1d8c1e970ebf73e2ea0b566573e93a0dd740fe7de1e5a09d614af0910df78802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819f6589590ff2975513adbce6e31e142f416d82357be47daa39069fe20cf0fd 0.600000000000 1692101 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": 1205414, "vin": [ { "gen": { "height": 1205404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819f6589590ff2975513adbce6e31e142f416d82357be47daa39069fe20cf0fd" } } ], "extra": [ 1, 143, 29, 140, 30, 151, 14, 191, 115, 226, 234, 11, 86, 101, 115, 233, 58, 13, 215, 64, 254, 125, 225, 229, 160, 157, 97, 74, 240, 145, 13, 247, 136, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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