Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64f9b9568ffa3c006386c20779dc3f933895e5070177eaa2ea1d684cd285537

Tx prefix hash: 3c57fafc710aff9d3755527578d72a8cf88425745d2f11f94cda895b606c395d
Tx public key: 3ae50091dce0ac31e6e9ae8d5acb0dfe73d534214d04afab292045f1d6926994
Timestamp: 1574433736 Timestamp [UCT]: 2019-11-22 14:42:16 Age [y:d:h:m:s]: 05:008:23:49:21
Block: 14513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149823 RingCT/type: yes/0
Extra: 013ae50091dce0ac31e6e9ae8d5acb0dfe73d534214d04afab292045f1d6926994021100000002b63f0b49000000000000000000

1 output(s) for total of 549.431166607000 dcy

stealth address amount amount idx
00: 22dc653cd3df04c2d07667562bf4edcfb1f8aa6dc63e0e4585aec2526f2378b5 549.431166607000 18484 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": 14523, "vin": [ { "gen": { "height": 14513 } } ], "vout": [ { "amount": 549431166607, "target": { "key": "22dc653cd3df04c2d07667562bf4edcfb1f8aa6dc63e0e4585aec2526f2378b5" } } ], "extra": [ 1, 58, 229, 0, 145, 220, 224, 172, 49, 230, 233, 174, 141, 90, 203, 13, 254, 115, 213, 52, 33, 77, 4, 175, 171, 41, 32, 69, 241, 214, 146, 105, 148, 2, 17, 0, 0, 0, 2, 182, 63, 11, 73, 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